London | 26-SDC-Mar | Ebrahim Beiati-Asl | Sprint 2 | Chat App frontend and backend#75
London | 26-SDC-Mar | Ebrahim Beiati-Asl | Sprint 2 | Chat App frontend and backend#75ebrahimbeiati wants to merge 1 commit into
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Code works on normal circumstances. My comments are mainly surrounding handling of
errors and unusual user input.
The README has this requirement:
It must also support at least one additional feature.
Can you describe the additional features you have implemented?
| app.post("/messages", (req, res) => { | ||
| const message = req.body; | ||
| messages.push(message); | ||
| res.status(201).json(message); |
There was a problem hiding this comment.
What's the reason to embed the received user message in the response?
Note: Normally we should also validate the message, but in this exercise let's assume the message format is always valid. That is, let's assume the received message is always sent by the code in script.js.
There was a problem hiding this comment.
I return the created message because the server adds the timestamp, so sending it back lets the client know the final version on the server. But in this exercise the frontend doesn’t use the POST response anyway, since it reloads all messages after sending, so returning it isn’t strictly necessary.
|
Changes look good. There is still an unanswered question (in the comment which I haven't marked as resolved), and an unaddressed issue related to describing the extra features in the PR description. |
|
The spec says
Can you think of a place to share that info so that people interested in your implementation can easily find out what extra features you have implemented? |
|
There are too many files committed in this pull request. Please check and make sure you have not accidentally committed a cache, virtual environment, or npm package directory. If this PR is not coursework, please add the NotCoursework label (and message on Slack in #cyf-curriculum or it will probably not be noticed). If this PR needs reviewed, please add the 'Needs Review' label to this PR after you have resolved the issues listed above. |
|
There are too many files committed in this pull request. Please check and make sure you have not accidentally committed a cache, virtual environment, or npm package directory. If this PR is not coursework, please add the NotCoursework label (and message on Slack in #cyf-curriculum or it will probably not be noticed). If this PR needs reviewed, please add the 'Needs Review' label to this PR after you have resolved the issues listed above. |
|
There are too many files committed in this pull request. Please check and make sure you have not accidentally committed a cache, virtual environment, or npm package directory. If this PR is not coursework, please add the NotCoursework label (and message on Slack in #cyf-curriculum or it will probably not be noticed). If this PR needs reviewed, please add the 'Needs Review' label to this PR after you have resolved the issues listed above. |
|
Commit 52f1240 introduced 1000+ files to this PR.
Can you fix it? I will mark this PR as Complete first. |
|
There are too many files committed in this pull request. Please check and make sure you have not accidentally committed a cache, virtual environment, or npm package directory. If this PR is not coursework, please add the NotCoursework label (and message on Slack in #cyf-curriculum or it will probably not be noticed). If this PR needs reviewed, please add the 'Needs Review' label to this PR after you have resolved the issues listed above. |
1 similar comment
|
There are too many files committed in this pull request. Please check and make sure you have not accidentally committed a cache, virtual environment, or npm package directory. If this PR is not coursework, please add the NotCoursework label (and message on Slack in #cyf-curriculum or it will probably not be noticed). If this PR needs reviewed, please add the 'Needs Review' label to this PR after you have resolved the issues listed above. |




Learners, PR Template
Self checklist
Backend
https://xwc7hmpmk5kvt9ktptcvuuke.hosting.codeyourfuture.io
Frontend
https://uretqju43s9008b1nyjk586m.hosting.codeyourfuture.io
Description
Additional Feature
Auto‑scroll: The chat automatically scrolls to the newest message when messages load.